Tech

15 resort friends have been injured by chlorine poisoning as a result of Microsoft’s international electronic mail outage

Microsoft’s worldwide 365 and Outlook outage had real-world consequences after it cut off email alerts for a German hotel’s pool safety system. The German outlet Westdeutscher Rundfunk (WDR) said several people were injured at a Phantasialand hotel on Friday after its email system failed to deliver a safety alert about elevated chlorine levels in the pool, as spotted earlier by NotebookCheck and TechRadar.

A machine-translated Facebook post from a German fire department said it responded to a Phantasialand hotel after a “technical malfunction” caused an excessive amount of chlorine to enter a swimming pool, resulting in chlorine gas leaking into the surrounding area. As 15 people were affected by the incident, including four who were transported to the hospital

Microsoft has since published a post-incident report about the outage, and EVP Charles Lamanna posted an abridged version last night on X. The company says three factors contributed significantly to the incident, including a bug introduced in a previous update in July. This, coupled with a surge in load following an earlier Teams outage and an “unrelated issue” from the previous day that knocked out nearly 14 percent of its server capacity, activated the conditions for the “latent” bug in the July update to rear its head, which “caused requests to build up until servers ultimately stopped responding” during the peak traffic window in the US on Thursday.

The outage lasted from Thursday afternoon and well into Friday morning for many businesses on the East Coast, before Microsoft said service was fully restored on Sunday. “Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again,” Microsoft says. “Our normally automated recovery processes were not designed to restore service from this broad unresponsive state.” Microsoft adds that it couldn’t “quickly revert the change” because the defect was a latent bug from several months ago.

Source: www.theverge.com

Show More

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button